|
|
 |
|
|
|
|
that the funds won't be available for 10 business days. After the teller enters the amount of the deposit, the application applies the deposit to the account in a temporary balance separate from the regular balance, until the funds' availability date has been reached. The application persists the deposit transaction to the account repository. |
|
|
|
|
|
|
|
|
If the application discovers that the account has been frozen by the government, the application notifies the teller. Perform the use case Canceling a Transaction. |
|
|
|
|
|
|
|
|
To determine the forms needed for this use case, look for clues about displaying information to the user or prompting the user for some information. Also, you might find clues that suggest that the user needs to be updated with the current state of processing. (Fortunately, you covered this requirement with frmCheckAccountStatus.) |
|
|
|
|
|
|
|
|
The first paragraph is a generic description of transactions that are processed. Because depositing and withdrawing funds have similar tasks, they were encapsulated generically in this use case. This is further justification for the frmMDI form. In the second sentence, you read that the applicationprompts the teller to verify that the customer is authorized to deposit to or withdraw funds from the account. Aha! This requirement isn't incorporated into our list of forms. The application must prompt the user about something. If you study this enough, you see that this is basically a message box. Given a controller class for this use case, TransactionProcessor, you need the following method: |
|
|
|
|
|
|
|
|
This is short for display authorization message to teller, reminding him or her to make sure the user has valid identification. Use the Visual Basic MsgBox command to display the incoming message. |
|
|
|
|
|
|
|
|
Reading further, if the customer is authorized to make a transaction, The application displays details about the account, including the customer's full name, Social Security number, account status, and account balance. Now you need an Account Detail form. The code name of this form is frmAccountDetail. The fields on this form include |
|
|
|
|
|
|
|
|
First Name (lblAccountDetail(0), txtAccountDetail(0)) |
|
|
|
|
|
|
|
|
Last Name (lblAccountDetail(1), txtAccountDetail(1)) |
|
|
|
|
|
|
|
|
Social Security Number (lblAccountDetail(2), txtAccountDetail(2)) |
|
|
|
|
|
|
|
|
Account Status (lblAccountDetail(3), txtAccountDetail(3)) |
|
|
|
|
|
|
|
|
Account Balance (lblAccountDetail(4), txtAccountDetail(4)) |
|
|
|
|
|
|
|
|
To keep this example simple, ignore other customer attributes such as address, phone number, and those with which you're probably already familiar. Next, you read that if |
|
|
|
|
|